Non-disruptively merging coordinated timing networks

ABSTRACT

Coordinated timing networks are dynamically merged into a single coordinated timing network. This merge occurs without taking down any of the servers. Each server of the merged coordinated timing network has the same coordinated timing network identifier (CTN ID), and the merged coordinated timing network has one selected primary time server. Optionally, the merged coordinated timing network may include a backup time server and an arbiter.

BACKGROUND

One or more aspects relate, in general, to coordinated timing networks,and in particular, to merging coordinated timing networks.

A Coordinated Timing Network (CTN) is a network in which multipledistinct computing systems maintain time synchronization to form thecoordinated timing network. Systems in the coordinated timing networkemploy a message based protocol, referred to as a Server Time Protocol(STP), to pass timekeeping information between the systems overexisting, high-speed data links. This enables the time of day (TOD)clocks at each system to be synchronized to the accuracy required intoday's high-end computing systems. Since the protocol makes use oftechnology within a computing system, synchronization accuracy scales astechnology improves. A computing system that provides time to othercomputing systems is referred to as a time server or server herein.

Within a coordinated timing network for STP, there is to be only oneserver acting as the source of time for the network (referred to as theprimary time server). If there is more than one time source, the twosources could diverge leading to a data integrity exposure. Likewise, ifthere is no single server acting as the source of time for the network,the clocks on the multiple servers could drift apart, raising a dataintegrity exposure in that way.

Customers using the Server Time Protocol have encountered situations inwhich multiple coordinated timing networks are to be merged into asingle coordinated timing network. However, to accomplish this, one ormore of the servers needs to be brought down. This is very disruptive tothe customers' business and usually means a loss of business andrevenue.

SUMMARY

Shortcomings of the prior art are overcome and additional advantages areprovided through the provision of a computer program product formanaging coordinated timing networks. The computer program productcomprises a storage medium readable by a processing circuit and storinginstructions for execution by the processing circuit for performing amethod. The method includes, for instance, determining that a pluralityof coordinated timing networks are to be merged into a singlecoordinated timing network (CTN); and based on determining that theplurality of coordinated timing networks are to be merged, merging theplurality of coordinated timing networks into the single coordinatedtiming network, wherein the merging is performed non-disruptively inthat servers of the plurality of coordinated timing networks continueprocessing during the merging.

Computer-implemented methods and systems relating to one or more aspectsare also described and claimed herein. Further, services relating to oneor more aspects are also described and may be claimed herein.

Additional features and advantages are realized through the techniquesdescribed herein. Other embodiments and aspects are described in detailherein and are considered a part of the claimed aspects.

BRIEF DESCRIPTION OF THE DRAWINGS

One or more aspects are particularly pointed out and distinctly claimedas examples in the claims at the conclusion of the specification. Theforegoing and objects, features, and advantages of one or more aspectsare apparent from the following detailed description taken inconjunction with the accompanying drawings in which:

FIG. 1 depicts one example of a coordinated timing network;

FIGS. 2A-2B depict servers of coordinated timing networks to be merged,in accordance with an aspect of the present invention;

FIG. 3 shows a result of merging coordinated timing networks, inaccordance with an aspect of the present invention;

FIG. 4 depicts one embodiment of logic to merge coordinated timingnetworks into a single coordinated timing network, in accordance with anaspect of the present invention;

FIG. 5 depicts one example of a new stratum-1 configuration informationblock used in accordance with an aspect of the present invention;

FIG. 6 depicts one embodiment of a cloud computing node;

FIG. 7 depicts one embodiment of a cloud computing environment; and

FIG. 8 depicts one example of abstraction model layers.

DETAILED DESCRIPTION

In accordance with one or more aspects, multiple coordinated timingnetworks are merged into a single coordinated timing network (CTN). Thismay be driven by a number of situations, including, but not limited to,changes internal to a business, system consolidation efforts, businessmergers and/or reversing a temporary splitting of a coordinating timingnetwork. Previously, customers have merged coordinated timing networksby taking down the partitions (e.g., logical partitions of the server),changing the configuration, and then bringing the partitions back upagain as members of a new CTN. This process of bringing down thepartitions to merge the CTNs is costly and inefficient.

Thus, in accordance with an aspect of the present invention, acoordinated timing network merging capability is provided that enables aCTN merge to be carried out dynamically, without shutting down any ofthe partitions or the servers on which the partitions are running. Thatis, a merging capability is provided that enables customers to safelymerge coordinated timing networks without enduring the expense of asystem outage. When the merge is complete, the separate CTNs will be apart of a larger CTN sharing time and connectivity across the larger setof servers.

One embodiment of a coordinated timing network is described withreference to FIG. 1. In this example, a coordinated timing network 100includes a plurality of servers 102 coupled to one another via one ormore STP links 104. For example, the plurality of servers 102 includesServer A 102 a and Server B 102 b. Although in this example, two serversare depicted, coordinated timing network 100 may include additionalservers. Each server is coupled to a support element 106, which isfurther coupled to a hardware management console 108. The hardwaremanagement console may be the same console or a different console foreach support element.

As examples, each server is a central electronics complex based on thez/Architecture offered by International Business Machines Corporation(IBM); the hardware management console is, for instance, a personalcomputer, such as an Intel-based personal computer with a DVD-RAM(digital video disk-random access memory), as a particular example, orother type of computer or processing device that includes functionalityto provide a standard interface for configuring and operatingpartitioned and SMP (Symmetric Multiprocessing) systems, such as Systemz offered by International Business Machines Corporation; and eachsupport element is, for instance, a workstation coupled to the centralelectronics complex used for monitoring and operating a system. Examplehardware management consoles and support elements are based ontechnology offered by International Business Machines Corporation.z/Architecture is a registered trademark of International BusinessMachines Corporation, Armonk, N.Y., USA. One embodiment of thez/Architecture is described in “z/Architecture Principles of Operation,”IBM Publication No. SA22-7832-10, March 2015, which is herebyincorporated herein by reference in its entirety.

Servers of multiple coordinated timing networks are depicted in FIGS.2A-2B. Referring initially to FIG. 2A, a first coordinated timingnetwork 100 a (referred to herein as CTN A) includes a plurality ofservers 102 (e.g., servers 102 a-102 d), and each server 102 may includeone or more partitions 200 (e.g., logical partitions). Each partition ispart of a particular Sysplex (system complex of servers), and thesysplex of a particular partition is indicated by a letter (e.g., letterA, in this example). Thus, partitions 200 a are part of Sysplex A.

Further, in one example, one of the servers, e.g., server 102 a (alsoreferred to herein as Server 1), is a primary time server (PTS) 210 aproviding current time for coordinated timing network 100 a. Further,server 102 b is a backup time server (BTS) 212 a for coordinated timingnetwork 100 a. Yet further, another server, e.g., server 102 c, is anarbiter (ARB) 214 a for coordinated timing network 100 a. The arbiterserver facilitates determination of a failure of the primary timeserver. As shown in FIG. 2A, each server is part of one coordinatedtiming network as indicated by a CTN ID 250 a (e.g., CTN ID 1) in eachserver 102.

Although certain servers are indicated as providing the timing roles ofprimary time server, backup time server and arbiter, in one embodiment,these roles are provided by the servers in conjunction with theirsupport elements.

Now, referring to FIG. 2B, a coordinated timing network 100 b (referredto herein as CTN B) includes, for instance, a plurality of servers, suchas servers 102 e-102 g. Each server includes one or more partitions 200,and each partition is part of a sysplex, such as Sysplex B, as indicatedby 200 b.

Further, in one example, one of the servers, server 102 e (also referredto herein as Server B), is a primary time server (PTS) 210 b providingcurrent time for coordinated timing network 100 b. Further, server 102 fis a backup time server (BTS) 212 b for coordinated timing network 100b. Yet further, another server, e.g., server 102 g, is an arbiter (ARB)214 b for coordinated timing network 100 b. As shown in FIG. 2B, eachserver is part of one coordinated timing network as indicated by a CTNID 250 b (e.g., CTN ID 2) in each server 102.

Again, although certain servers are indicated as providing the timingroles of primary time server, backup time server and arbiter, in oneembodiment, these roles are provided by the servers in conjunction withtheir support elements.

Each CTN may have more or less servers than described herein. The numberof servers depicted in each CTN is just an example.

Servers in a CTN that are in the synchronized state are assigned avalue, referred to as a stratum level, that specifies the number ofservers between it and a primary time server. A primary time serveroperates at a stratum level of 1; secondary time servers operate at astratum level of 2 or above, which increases as the number of servers inthe timing path to the stratum-1 increases. In general, the quality oftimekeeping information decreases as the stratum level increases. Aserver that is unsynchronized is assigned a stratum level of 0.

In one example, a customer would like to merge the two coordinatedtiming networks of FIGS. 2A-2B into a single coordinated timing network,as depicted in FIG. 3. As shown in FIG. 3, a coordinated timing network300 includes servers 102 a-102 d of coordinated timing network 100 a andservers 102 e-102 g of coordinated timing network 100 b. One of theservers (e.g., server 102 a) is selected as the primary time server 302for coordinated timing network 300, another server (e.g., server 102 b)is selected as the backup time server 304, and yet a further server(e.g., server 102 c) is selected as an arbiter 306. Since thecoordinated timing networks have been merged, server 102 e no longer hasthe role of primary time server, server 102 f no longer has the role ofbackup time server, and server 102 g no longer has the role of arbiter.

One embodiment of logic used to merge multiple coordinated timingnetworks into a single coordinated timing network is described withreference to FIG. 4. In one example, one or more processors of one ormore support elements and/or one or more servers are used to performaspects of the logic to merge the coordinated timing networks.

Referring to FIG. 4, initially the servers are connected via couplinglinks, STEP 400. For instance, a manual operation is performed toconnect the cables, and an operator action is performed to configurethese coupling links for use and to bring them online. With this set-up,server 102 e (i.e., Server B) registers itself, e.g., at its supportelement, as a probe into the PTS of server 102 a (i.e., Server 1), toenable server 102 e to read the time of the PTS, and to enable the PTSto recognize server 102 e in this regard. This establishes intent, andallows timing information to flow from server 102 a to server 102 e.

Additionally, server 102 e uses server 102 a as an external time source(ETS), STEP 402. Server 102 e steers toward the time presented by server102 a, thus bringing it into synchronization with CTN 100 a time, STEP404. For example, server 102 e steers its time of day clock (TOD) to thetime provided by the time of day clock of server 102 a.

A determination is made as to whether the times are within a configuredamount of one another, INQUIRY 408. If the times are not close enough,then processing continues at STEP 404. However, if the times are withinthe configured amount, then the clocks of CTN 100 a and CTN 100 b areconsidered synchronized, STEP 410.

Then, server 102 e requests server 102 a to generate and distribute anew configuration, STEP 412. In particular, server 102 e sends a messageto server 102 a requesting server 102 e to generate and distribute a newstratum-1 configuration that includes configuration information for themerged CTN, STEP 412.

Based on the request, server 102 a creates a new stratum-1 configurationinformation block, and distributes this configuration information block,STEP 414.

As one example, with reference to FIG. 5, a new stratum-1 configurationinformation block 500 includes a plurality of fields that includeconfiguration information, such as, for instance:

-   -   A primary stratum-1 node descriptor 502: This field is valid        when a single server, dual server or triad definition has been        specified in the configuration type field (discussed below) and        includes the node descriptor of the new primary stratum-1 node;    -   An alternate stratum-1 node descriptor 504: This field is valid        when a dual server or triad definition has been specified in the        configuration type field and includes the node descriptor of the        new alternate stratum-1 node (i.e., the backup time server);    -   An optional arbiter node descriptor 506: This field is valid        when a triad definition has been specified in the configuration        type field and includes the node descriptor of the new arbiter        node;    -   A stratum-1 configuration update time 508: This field includes a        timestamp that indicates when the values in this block are to        become current for the CTN;    -   A configuration type 510: This field specifies the type of        stratum-1 configuration, as defined below:        -   Null definition—None of the node descriptors are valid.        -   Single server definition—Only the primary stratum-1 node            descriptor is valid. In a single server configuration, if            the primary time server is lost, synchronized time for the            CTN is lost, since there is no backup.        -   Dual server definition—The primary stratum-1 and alternate            stratum-1 (backup time server) node descriptors are valid.            In a dual server configuration, a mechanism is provided for            an alternate server to be able to take over the role of an            active stratum-1 server for the CTN.        -   Triad definition—The primary stratum-1, alternate stratum-1            and arbiter node descriptors are valid. In a triad            configuration, a primary time server, a backup time server            and an arbiter are provided. The arbiter server may be used            to determine a failure of the primary time server.    -   A merge indicator 512: When the merge indicator (e.g., a bit) is        set to one, it indicates that this is a special configuration        that will be used to merge multiple coordinated timing networks        into one coordinated timing network. The systems that are        already a part of this CTN will simply activate this        configuration. However, the primary time source of the merging        CTN will add a CTN ID in this configuration block to match that        of the new CTN and send it out to all of the servers in its        configuration. At activation time, they will change their CTN ID        and merge into a single CTN.    -   A new CTN ID 514: This field specifies a new CTN identifier        identifying the new CTN.

Although various fields are described herein, more, less and/ordifferent fields may be included in the new stratum-1 configurationinformation block without departing from a spirit of one or more aspectsof the present invention.

Returning to FIG. 4, STEP 414, server 102 a populates the block with,for instance, the designated primary time server, the alternate timeserver, the arbiter, and/or an update time, as well as sets the mergeindicator (e.g., to one). Then, server 102 a distributes the newstratum-1 configuration to the servers in CTN A and to the primary timeserver (e.g., server 102 e) in CTN B. For instance, server 102 a (e.g.,optionally, using its support element) includes the configurationinformation block or at least an indication of the block in a requestblock of a command, such as an STP modify stratum-1 configurationcommand, and distributes that command to the servers in CTN A and to theprimary time server in CTN B.

Server 102 e receives the command, reads the configuration, adds amodified CTN ID (i.e., the CTN ID of CTN 100 a) to the configurationblock, and distributes it to the other servers in CTN 100 b, STEP 416.Thereafter, at the time indicated in the stratum-1 configuration, all ofthe servers of the two CTNs activate their configurations and becomepart of a single new coordinated timing network lead by server 102 a,STEP 418. This is accomplished without bringing down the servers and/orthe partitions executing on the servers.

As a result of becoming a single CTN, each server has the same CTN ID asreflected in FIG. 3 at 310, and each server uses server 102 a as itstime source.

Described in detail herein is a CTN merging capability that dynamicallymerges multiple coordinated timing networks into a single coordinatedtiming network without shutting down any of the partitions and/orservers. Although it is indicated herein that the servers perform or areinvolved in certain actions, these actions may be performed by theservers, by the support elements coupled to the servers and/or by acombination of the servers and the support elements. Thus, the term“component of a server” used herein may include the server, the supportelement, and/or the server with the support element.

One or more aspects may relate to cloud computing.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as Follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as Follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as Follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forloadbalancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 6, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 6, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 7, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 7 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 8, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 7) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 8 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and merge processing 96.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

In addition to the above, one or more aspects may be provided, offered,deployed, managed, serviced, etc. by a service provider who offersmanagement of customer environments. For instance, the service providercan create, maintain, support, etc. computer code and/or a computerinfrastructure that performs one or more aspects for one or morecustomers. In return, the service provider may receive payment from thecustomer under a subscription and/or fee agreement, as examples.Additionally or alternatively, the service provider may receive paymentfrom the sale of advertising content to one or more third parties.

In one aspect, an application may be deployed for performing one or moreembodiments. As one example, the deploying of an application comprisesproviding computer infrastructure operable to perform one or moreembodiments.

As a further aspect, a computing infrastructure may be deployedcomprising integrating computer readable code into a computing system,in which the code in combination with the computing system is capable ofperforming one or more embodiments.

As yet a further aspect, a process for integrating computinginfrastructure comprising integrating computer readable code into acomputer system may be provided. The computer system comprises acomputer readable medium, in which the computer medium comprises one ormore embodiments. The code in combination with the computer system iscapable of performing one or more embodiments.

Although various embodiments are described above, these are onlyexamples. For example, computing environments of other architectures canbe used to incorporate and use one or more embodiments. Further,different instructions, instruction formats, instruction fields and/orinstruction values may be used. Many variations are possible.

Further, other types of computing environments can benefit and be used.As an example, a data processing system suitable for storing and/orexecuting program code is usable that includes at least two processorscoupled directly or indirectly to memory elements through a system bus.The memory elements include, for instance, local memory employed duringactual execution of the program code, bulk storage, and cache memorywhich provide temporary storage of at least some program code in orderto reduce the number of times code must be retrieved from bulk storageduring execution.

Input/Output or I/O devices (including, but not limited to, keyboards,displays, pointing devices, DASD, tape, CDs, DVDs, thumb drives andother memory media, etc.) can be coupled to the system either directlyor through intervening I/O controllers. Network adapters may also becoupled to the system to enable the data processing system to becomecoupled to other data processing systems or remote printers or storagedevices through intervening private or public networks. Modems, cablemodems, and Ethernet cards are just a few of the available types ofnetwork adapters.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used herein, thesingular forms “a”, “an” and “the” are intended to include the pluralforms as well, unless the context clearly indicates otherwise. It willbe further understood that the terms “comprises” and/or “comprising”,when used in this specification, specify the presence of statedfeatures, integers, steps, operations, elements, and/or components, butdo not preclude the presence or addition of one or more other features,integers, steps, operations, elements, components and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below, if any, areintended to include any structure, material, or act for performing thefunction in combination with other claimed elements as specificallyclaimed. The description of one or more embodiments has been presentedfor purposes of illustration and description, but is not intended to beexhaustive or limited to in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the art. Theembodiment was chosen and described in order to best explain variousaspects and the practical application, and to enable others of ordinaryskill in the art to understand various embodiments with variousmodifications as are suited to the particular use contemplated.

What is claimed is:
 1. A computer program product for managingcoordinated timing networks, the computer program product comprising: anon-transitory readable storage medium readable by a processing circuitand storing Instructions for execution by the processing circuit forperforming a method comprising: determining that a plurality ofcoordinated timing networks are to be merged into a single coordinatedtiming network (CTN), the plurality of coordinated timing networksincluding, at least, one coordinated timing network and anothercoordinated timing network, wherein the one coordinated timing networkcomprises one set of servers and the other coordinated timing networkcomprises another set of servers, wherein each of the plurality ofcoordinated timing networks and the single coordinated timing network isa network in which multiple distinct computing systems maintain timesynchronization to form a coordinated timing network, and providessynchronization of time of day clocks of the multiple distinct computingsystems; and based on determining that the plurality of coordinatedtiming networks are to be merged, merging the plurality of coordinatedtiming networks into the single coordinated timing network, wherein themerging is performed non-disruptively in that servers of the pluralityof coordinated timing networks continue processing during the merging,and wherein the merging comprises: providing, by a server of the one setof servers designated to be a primary time server of the one coordinatedtiming network, a configuration block including information relating toa designated primary node of the single coordinated timing network, aconfiguration update time, and a merge indicator set to indicate thatthe configuration block will be used for the merging; the primary timeserver of the one coordinated timing network distributing theconfiguration block to the one set of servers of the one coordinatedtiming network and to a server designated as a primary time server inthe other set of servers of the other coordinated timing network; theprimary time server in the other set of servers of the other coordinatedtiming network modifying the configuration block by adding a new CTNidentifier to the configuration block and subsequently distributing themodified configuration block to the other set of servers of the othercoordinating timing network; and at a time indicated by theconfiguration update time, each server of the one set of servers and theother set of servers activating a new configuration based on theconfiguration block and the modified configuration block, respectively,to become part of the single coordinated timing network.
 2. The computerprogram product of claim 1, wherein the merging comprises: steering theother coordinated timing network to a time of the one coordinated timingnetwork to synchronize the other coordinated timing network with the onecoordinated timing network.
 3. The computer program product of claim 2,wherein the steering comprises: determining whether a first time of theone coordinated timing network and a second time of the othercoordinated timing network are within a configured amount from oneanother; and based on being within the configured amount, the othercoordinated timing network is in synchronization with the onecoordinated timing network.
 4. The computer program product of claim 1,wherein the distributing the configuration block and the modifiedconfiguration block further comprises: using a component of the serverof the one set of servers designated to be the primary time server ofthe one coordinated timing network to distribute the configuration blockto a component of the server designated to be the primary time server inthe other set of servers; and providing by the component of the serverdesignated to be the primary time server in the other set of servers ofthe other coordinated timing network the modified configuration block tothe other set of servers.
 5. The computer program product of claim 4,wherein the method further comprises: receiving by components of theother set of servers the modified configuration block; and activatingthe new configuration by the components of the other set of servers. 6.The computer program product of claim 1, wherein the configuration blockfurther includes another indication of which other server of the one setof servers or the other set of servers is to be a backup time server forthe single coordinated timing network.
 7. A computer system for managingcoordinated timing networks, the computer system comprising: a memory;and a processor in communication with the memory, wherein the computersystem is configured to perform a method, said method comprising:determining that a plurality of coordinated timing networks are to bemerged into a single coordinated timing network (CTN), the plurality ofcoordinated timing networks including, at least, one coordinated timingnetwork and another coordinated timing network, wherein the onecoordinated timing network comprises one set of servers and the othercoordinated timing network comprises another set of servers, wherein aeach of the plurality of coordinated timing networks and the singlecoordinated timing network is a network in which multiple distinctcomputing systems maintain time synchronization to form a coordinatedtiming network, and provides synchronization of time of day clocks ofthe multiple distinct computing systems; and based on determining thatthe plurality of coordinated timing networks are to be merged, mergingthe plurality of coordinated timing networks into the single coordinatedtiming network, wherein the merging is performed non-disruptively inthat servers of the plurality of coordinated timing networks continueprocessing during the merging, wherein the merging comprises: providing,by a server of the one set of servers designated to be a primary timeserver of the one coordinated timing network, a configuration blockincluding information relating to a designated primary node of thesingle coordinated timing network, a configuration update time, and amerge indicator set to indicate that the configuration block will beused for the merging; the primary time server of the one coordinatedtiming network distributing the configuration block to the one set ofservers of the one coordinated timing network and to a server designatedas a primary time server in the other set of servers of the othercoordinated timing network; the primary time server in the other set ofservers of the other coordinated timing network modifying theconfiguration block by adding a new CTN identifier to the configurationblock and subsequently distributing the modified configuration block tothe other set of servers of the other coordinating timing network; andat a time indicated by the configuration update time, each server of theone set of servers and the other set of servers activating a newconfiguration based on the configuration block and the modifiedconfiguration block, respectively, to become part of the singlecoordinated timing network.
 8. The computer system of claim 7, whereinthe merging comprises: steering the other coordinated timing network toa time of the one coordinated timing network to synchronize the othercoordinated timing network with the one coordinated timing network. 9.The computer system of claim 8, wherein the steering comprises:determining whether a first time of the one coordinated timing networkand a second time of the other coordinated timing network are within aconfigured amount from one another; and based on being within theconfigured amount, the other coordinated timing network is insynchronization with the one coordinated timing network.
 10. Thecomputer system of claim 7, wherein the distributing the configurationblock and the modified configuration block further comprises: using acomponent of the server of the one set of servers designated to be theprimary time server of the one coordinated timing network to distributethe configuration block to a component of the server designated to bethe primary time server in the other set of servers; and providing bythe component of the server designated to be the primary time server inthe other set of servers of the other coordinated timing network themodified configuration block to the other set of servers.
 11. Thecomputer system of claim 10, wherein the method further comprises:receiving by components of the other set of servers the new modifiedconfiguration block; and activating the new configuration by thecomponents of the other set of servers.
 12. The computer system of claim7, wherein the configuration block further includes another indicationof which other server of the one set of servers or the other set ofservers is to be a backup time server for the single coordinated timingnetwork.
 13. A computer-Implemented method of managing coordinatedtiming networks, the computer-implemented method comprising: determiningthat a plurality of coordinated timing networks are to be merged into asingle coordinated timing network (CTN), the plurality of coordinatedtiming networks including, at least, one coordinated timing network andanother coordinated timing network, wherein the one coordinated timingnetwork comprises one set of servers and the other coordinated timingnetwork comprises another set of servers, wherein each of the pluralityof coordinated timing networks and the single coordinated timing networkis a network in which multiple distinct computing systems maintain timesynchronization to form a coordinated timing network, and providessynchronization of time of day clocks of the multiple distinct computingsystems; and based on determining that the plurality of coordinatedtiming networks are to be merged, merging the plurality of coordinatedtiming networks into the single coordinated timing network, wherein themerging is performed non-disruptively in that servers of the pluralityof coordinated timing networks continue processing during the merging,and wherein the merging comprises: providing, by a server of the one setof servers designated to be a primary time server of the one coordinatedtiming network, a configuration block including information relating toa designated primary node of the single coordinated timing network, aconfiguration update time, and a merge indicator set to indicate thatthe configuration block will be used for the merging; the primary timeserver of the one coordinated timing network distributing theconfiguration block to the one set of servers of the one coordinatedtiming network and to a server designated as a primary time server inthe other set of servers of the other coordinated timing network; theprimary time server in the other set of servers of the other coordinatedtiming network modifying the configuration block by adding a new CTNidentifier to the configuration block and subsequently distributing themodified configuration block to the other set of servers of the othercoordinating timing network; and at a time indicated by theconfiguration update time, each server of the one set of servers and theother set of servers activating a new configuration based on theconfiguration block and the modified configuration block, respectively,to become part of the single coordinated timing network.
 14. Thecomputer-implemented method of claim 13, wherein the merging comprises:steering the other coordinated timing network to a time of the onecoordinated timing network to synchronize the other coordinated timingnetwork with the one coordinated timing network.
 15. Thecomputer-implemented method of claim 14, wherein the steering comprises:determining whether a first time of the one coordinated timing networkand a second time of the other coordinated timing network are within aconfigured amount from one another; and based on being within theconfigured amount, the other coordinated timing network is insynchronization with the one coordinated timing network.
 16. Thecomputer-implemented method of claim 13, wherein the distributing theconfiguration block and the modified configuration block furthercomprises: using a component of the server of the one set of serversdesignate to be the primary time server of the one coordinated timingnetwork to distribute the configuration block to a component of theserver designated to be the primary time server in the other set ofservers; and providing by the component of the server designated to bethe primary time server in the other set of servers of the othercoordinated timing network the modified configuration to the other setof servers.
 17. The computer-implemented method of claim 16, furthercomprising: receiving by components of the other set of servers themodified configuration block; and activating the new configuration bythe components of the other set of servers.
 18. The computer-implementedmethod of claim 13, wherein the configuration block further includesanother indication of which other server of the one set of servers orthe other set of servers is to be a backup time server for the singlecoordinated timing network.